Print

This section contains information about the latest release of the module such as release history, changes made to the current version and the list of known issues.

1.  Release History

October 02, 2008

Mailing List module v5.2.2 rev. 080929 for Sitecore CMS 5.3.2 is released.

Sitecore versions: tested with Sitecore CMS 5.3.1 rev. 071114.

Changes:

• Fixed: The Mailing List administration console displayed Japanese symbols incorrectly.
• Fixed: The Mailing List failed to send emails if the site used the https protocol.

July 29, 2008

Mailing List module v5.2.2 rev. 080523 for Sitecore CMS 5.3 is released.

Sitecore versions: tested with Sitecore CMS 5.3.1 rev. 071114.

Changes:

• Fixed: If anonymous access was disabled in the IIS security settings and the Mailing List setting ‘User’ contained a value with a domain name (for example, domain\user), this could cause an error while sending email messages.
• Fixed: When an email message was sent in the batch mode the performance degraded quickly for each new batch.

October 15, 2007

Mailing List module v5.2.2. for Sitecore CMS 5.3.1 is released

Sitecore versions: tested with Sitecore CMS 5.3.1 Build 070924.

Changes:

• Important Note: The Mailing List module now has no support for multiple site configuration.
• Fixed: Links to anchors inside the page are broken in the received mail.
• Fixed: Connection field is not shared.
• Fixed: If a message url contains a space you may get an error Bad request(HttpRequest 400) on sending email.
• Fixed: Mailing list could not be renamed if sql mail base is using

November 08, 2006

Mailing List module v5.2.0 is released.

2.  Known Issues

• A letter may not be sent if a website requires authentication (anonymous access is not enabled in IIS settings).

• When the MailingList module is installed along with the LDAP module, it is sometimes required that access is denied to the entire site for the Anonymous user. In this case the MailingList module stops sending mails. The reason lies in the chilkat library implementation.
  WorkAround:
  1) Open the properties of the current site
  2) Open the Directory Security tab
  3) Click the Edit button in the Anonymous access and authentification control group
  4) In the Authentificated access group select the checkbox Basic uthentification (password is sent in clear text) (Default domain and Realm fields should stay empty)
  IMPORTANT: you should store the login and password which should be used for connection to the server into User and Password fields in the Mailing List module configuration item (You can access it via Sitecore mainmenu: Sitecore » All Applications » Mailing List Module » Setting or ,using the Sitecore content editor, edit the item /sitecore/system/Modules/MailingList)
  5) Answer Yes in the dialog box that appears.

  Note: the solution can't be considered secure because user login and password are transmitted over the network without data encryption. This is not applicable for HTTPS (or SSL) protocol since HTTPS encrypts the session data using the SSL (Secure Socket Layer) protocol.When using the Send button in the editor to send mail, the page is not reloaded after the send operation is completed.

• The item of the sent mail is moved to the Sent folder, but the content tree is not refreshed.

• Due to the error in third-part email sender url mail pointing to some sites might be in incorrect format. Please use ‘Send Test mail’ to check the url mail format.

• If you add a subscriber to a new Mailing List, this subscriber will be resubscribed to the existing Mailing Lists. Statistics shows this as a simultaneous unsubscription of one subscriber and subscription of another, which does not influence the rating.

• If the RecipientUrlMails option is set to true, the emails will arrive without attachments.